--- id: TASK-015 title: Set glint as the editor for prose-based tool invocations (git/jj) status: "\U0001F7E6 Backlog" assignee: [] created_date: '2026-06-29 16:36' labels: - feature - release-2 dependencies: [] priority: medium ordinal: 15000 --- ## Description Adoption feature. $EDITOR is one slot for everything, so a coder must keep neovim there for code — but the prose-oriented editor calls (git commit/rebase/merge/tag messages, jj describe) can point at glint per-tool while $EDITOR stays the code editor. There is no OS-level text-vs-code split; it must be wired per tool. Provide a convenience in the config walkthrough (glint -c) or a small command that idempotently sets: - git: 'git config --global core.editor glint' (commit/rebase/merge/tag messages, git config -e) - jj: 'jj config set --user ui.editor glint' …and leaves $EDITOR / $VISUAL alone. Offer to undo. Document the manual one-liners in the README. One-shot editor mode already works: a tool calls 'glint ', the user edits, Ctrl+S saves, Ctrl+Q exits, the tool reads the saved file. Verify glint behaves cleanly when invoked on a non-.md tmpfile (e.g. COMMIT_EDITMSG) — it should still open/edit/save fine. Consider a save-on-quit prompt so an unsaved commit message isn't silently empty (the dirty-quit confirm largely covers this). Positioning: glint is the terminal WRITING app, owning prose edits, not the universal default editor. ## Acceptance Criteria - [ ] #1 A glint command / config step sets git core.editor (and jj ui.editor) to glint, leaving $EDITOR untouched - [ ] #2 It is idempotent and offers an undo/unset - [ ] #3 glint opens, edits, and saves cleanly when invoked one-shot on a non-.md tmpfile (e.g. git COMMIT_EDITMSG) - [ ] #4 README documents the manual git/jj one-liners